-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding redirect to /stac/stac when using twitcher #382
Conversation
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/2071/Result : failure BIRDHOUSE_DEPLOY_BRANCH : stac-redirect DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-216.rdext.crim.ca PAVICS-e2e-workflow-tests Pipeline ResultsTests URL : http://daccs-jenkins.crim.ca:80/job/PAVICS-e2e-workflow-tests/job/master/1315/NOTEBOOK TEST RESULTS |
@Nazim-crim do you mind summarizing the issue in DAC-580 here. I don't have access to that URL and I'm not sure what issue this is resolving. Thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Nazim-crim
I believe you also found out that the Magpie service/resources needed the nested stac/stac
as well to secure access properly?
To make sure one does not create resources directly under the stac
service, I think it would be wise to apply the permissions in https://github.com/bird-house/birdhouse-deploy/blob/master/birdhouse/optional-components/stac-public-access/config/magpie/config.yml.template#L11-L19 directly on a new stac
resource under the stac
service.
@mishaschwartz it's in the pr description |
Wait, I'm also confused why there's no Sorry, I should have noticed that earlier. |
And also the current dependency structure will mean that stac will always be enabled if
That seems confusing as well. There's some really weird things going on with the way this is set up. Am I looking at this wrong? |
I think we should remove the stac-public-access and in the default.env of all-public-access and just have the definition of providers and permissions in /stac/config/magpie . Would that make more sense or is there another reason to have it separate. @mishaschwartz @fmigneault |
@Nazim-crim I like your suggestion and I've made a branch with some suggested changes. Please check it out here (https://github.com/bird-house/birdhouse-deploy/compare/stac-permission-fixes) Let me know if you'd like to incorporate these changes in this PR or if you'd like me to open a different PR as well |
@mishaschwartz We can incorporate theses changes in this pr. Do you want me to pull your branch or are you gonna push it from your side here. Also just to make sure that there's a |
Sorry, I didn't see all the following comments. Was already working on the fix. |
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/2075/Result : failure BIRDHOUSE_DEPLOY_BRANCH : stac-redirect DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-133.rdext.crim.ca PAVICS-e2e-workflow-tests Pipeline ResultsTests URL : http://daccs-jenkins.crim.ca:80/job/PAVICS-e2e-workflow-tests/job/master/1318/NOTEBOOK TEST RESULTS |
@fmigneault no worries. That's funny, we were all working on the same thing. Let's use your PR and leave this one as is and I'll remove my branch once your PR is pulled in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Approuve the spirit of the PR. Will let Francis have the final say since he knows more about Magpie config.
Updated to take into account changes in #383. |
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/2078/Result : failure BIRDHOUSE_DEPLOY_BRANCH : stac-redirect DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-46.rdext.crim.ca PAVICS-e2e-workflow-tests Pipeline ResultsTests URL : http://daccs-jenkins.crim.ca:80/job/PAVICS-e2e-workflow-tests/job/master/1321/NOTEBOOK TEST RESULTS |
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/2079/Result : failure BIRDHOUSE_DEPLOY_BRANCH : stac-redirect DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-20.rdext.crim.ca PAVICS-e2e-workflow-tests Pipeline ResultsTests URL : http://daccs-jenkins.crim.ca:80/job/PAVICS-e2e-workflow-tests/job/master/1323/NOTEBOOK TEST RESULTS |
## Overview Move STAC service definitions under `components/stac` configuration. ## Changes **Non-breaking changes** - Move initial ``stac`` service Magpie definition under its component configuration. - Before this change, ``optional-components/stac-public-access`` was mandatory since the ``stac`` service under Magpie was not created otherwise, leading to "*service not found*" error when requesting the ``/stac`` endpoint. - Ensure that the first ``stac`` resource under ``stac`` service in Magpie is created by default. Without this resource being defined initially, it is very easy to forget creating it, which would not take into account the required ``/stac/stac`` request path to properly resolve the real endpoints where STAC API is served. - Remove `optional-components/stac-public-access` dependency under `optional-components/all-public-access` to avoid indirectly enforcing `components/stac` when `optional-components/all-public-access` is enabled. Users that desire using `optional-components/stac-public-access` will have to add it explicitly to the list of `EXTRA_CONF_DIRS`. - Rename `optional-components/stac-public-access/config/magpie/config.yml.template` to `optional-components/stac-public-access/config/magpie/permissions.cfg` in order to align with permissions-specific contents as accomplished with other components. **Breaking changes** - n/a ## Related Issue / Discussion - Relates to #382
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/2082/Result : failure BIRDHOUSE_DEPLOY_BRANCH : stac-redirect DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-133.rdext.crim.ca Infrastructure deployment failed. Instance has not been destroyed. @matprov |
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/2083/Result : failure BIRDHOUSE_DEPLOY_BRANCH : stac-redirect DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-46.rdext.crim.ca Infrastructure deployment failed. Instance has not been destroyed. @matprov |
Overview
Fix redirect when behind twitcher to automatically redirect to /stac/stac
Related Issue / Discussion
Notes